An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hello, I would really appreciate if someone from Apple could take a look at this, as I believe there may be an issue with my submission or account. I submitted my app for review for the first time over a month ago, and it has been stuck in “Waiting for Review” ever since, with absolutely no updates. This delay is far beyond the typical review timeframes (which are usually just a few days). I have not received any rejection, feedback, or request for additional information. So far, I have already: Resubmitted the build Sent multiple support requests through App Store Connect Requested an expedited review (which was approved) Despite all of this, there has been no progress at all. I have also sent several support messages and emails, but unfortunately I have not received any response so far. It feels like my case is not being reviewed at all, which makes it very difficult to understand what is going wrong. The app is quite standard and does not contain anything that should require extended review. At this point, I am concerned that there might be: An issue with my developer account A submission stuck in the review queue Or some kind of internal flag that I am not aware of Has anyone experienced a similar situation where an app remained in “Waiting for Review” for over a month? And if anyone from Apple is reading this, could you please check if there is any issue with my submission? Any help or guidance would be greatly appreciated. Thank you.

Hello, I would really appreciate if someone from Apple could take a look at this, as I believe there may be an issue with my submission or account. I submitted my app for review for the first time over a month ago, and it has been stuck in “Waiting for Review” ever since, with absolutely no updates. This delay is far beyond the typical review timeframes (which are usually just a few days). I have not received any rejection, feedback, or request for additional information. So far, I have already: Resubmitted the build Sent multiple support requests through App Store Connect Requested an expedited review (which was approved) Despite all of this, there has been no progress at all. I have also sent several support messages and emails, but unfortunately I have not received any response so far. It feels like my case is not being reviewed at all, which makes it very difficult to understand what is going wrong. The app is quite standard and does not contain anything that should require extended review. At this point, I am concerned that there might be: An issue with my developer account A submission stuck in the review queue Or some kind of internal flag that I am not aware of Has anyone experienced a similar situation where an app remained in “Waiting for Review” for over a month? And if anyone from Apple is reading this, could you please check if there is any issue with my submission? Any help or guidance would be greatly appreciated. Thank you.

Hello, I would really appreciate if someone from Apple could take a look at this, as I believe there may be an issue with my submission or account. I submitted my app for review for the first time over a month ago, and it has been stuck in “Waiting for Review” ever since, with absolutely no updates. This delay is far beyond the typical review timeframes (which are usually just a few days). I have not received any rejection, feedback, or request for additional information. So far, I have already: Resubmitted the build Sent multiple support requests through App Store Connect Requested an expedited review (which was approved) Despite all of this, there has been no progress at all. I have also sent several support messages and emails, but unfortunately I have not received any response so far. It feels like my case is not being reviewed at all, which makes it very difficult to understand what is going wrong. The app is quite standard and does not contain anything that should require extended review. At this point, I am concerned that there might be: An issue with my developer account A submission stuck in the review queue Or some kind of internal flag that I am not aware of Has anyone experienced a similar situation where an app remained in “Waiting for Review” for over a month? And if anyone from Apple is reading this, could you please check if there is any issue with my submission? Any help or guidance would be greatly appreciated. Thank you.

I uploaded the first build of a new app, waited a week to get In Review. Then got rejected for a missing piece of metadata. I accidentally checked a box indicating I had age-related content which I don't - so I unchecked it, and replied to app review. A message came back the same day asking me to do what I just told them I did. I replied that I had already followed the required steps. Then just nothing for five days. I have no idea if my review was even progressing - with the status "Waiting for Review" and "Unresolved issues". So I had no choice but to cancel the submission and start over. Having been an iOS developer for more than ten years, App Review times have gotten completely unacceptable - to develop an application and have no idea how many weeks it's going to take to crawl through App Review only to be rejected for some trivial checkbox, and get kicked to the back of the queue.

I've published my app with subscriptions (app changed from paid to subscription model). I've have succesfully pass review process and app was published to App Store without subscription store, so no one can buy app (still working as paid, but will expire in few days forcing users to subscribe). I want to attach subscriptions to new build, but I can't - there are no options mentioned in documentation. I'm stuck. There is no any contact point to review team. I've created 3 cases, nobody reads them (oldest 3 weeks). The whole approval process looks broken, Apple team shouldn't approve app with subscriptions without subscriptions added to review. I must immediately publish my app with critical fixes, but I can't. I am devastated, i don't know what to do...

Dear App Review Team, Our app – Apple ID 6755677576 has been stuck in the “In review” status for over 10 days (since March 17, 2026). Normally, reviews begin within a few days, but in our case, it seems unusually delayed. Could you please clarify: • Is there a specific reason for this extended hold? • Is any action required from our side? • When can we expect the review to proceed? Thank you very much for your time and assistance.

Hi, I created an anti virus app that worked within the sandbox. It was non commercial essentially a test to find a marketable anti virus app that could work within the sandbox. App store review kept saying it was malicious over and over again then told us our developer account was pending termination. We have a lot of others app that are my only source of income. I managed to work myself out of homelessness by being an App Developer (I've been an app developer since 2009). Now I'm facing it again for innovation. Thanks David

Hi all, my mac app uses the "com.apple.security.temporary-exception.apple-events" entitlement. Originally the process was that one is allowed to use such an entitlement as long as one filed a bug to request a scripting target that would allow one to move away from it. Now, my app has been approved for years with that entitlement, but every 5th time or so I submit an update, my app gets rejected because I allegedly shouldn't use that entitlement. I then ask for clarification, repeating the statement about why i am using it, and then the app gets silently approved. Is there a better way to handle this? It is super annoying that every couple of updates I get this random delay and have to dispute stuff just to get my update through. The note for the entitlement already describes why I am using it, but it seems that some reviewers just ignore it and then, upon me repeating that note, the app gets approved... I would also be fine getting an official statement that Apple doesn't support my use of the entitlement anymore and I could communicate to my customers that this is why the feature will disappear in the app store version, but since my updates eventually get approved, the issue seems to be with the particular reviewer... Any ideas how to fix this? Thank you.

Is it mandatory for all developers to migrate to Xcode 26 starting from April 28, 2026? What happens if a developer submits or distributes a build created using Xcode 16 after April 28, 2026? Will it still be accepted or supported? Our app is distributed only via an internal company portal (not through the App Store). In this case, are we still required to build and distribute the app using Xcode 26 after April 28, 2026? If a hotfix is required before our next planned release (July 2026), how safe is it to use the UIDesignRequiresCompatibility flag as a temporary solution, assuming Xcode 26 becomes mandatory? Are there any risks or limitations associated with this approach? What are the potential issues if a team continues development on Xcode 16 while others have migrated to Xcode 26? For example, could there be compatibility, build, or integration challenges in such a mixed environment? If the UIDesignRequiresCompatibility flag is used as a temporary workaround, what would be the impact if Apple later removes support for this flag, especially with newer iOS versions (e.g., iOS 26+)? For users who already have the app installed with this flag enabled For users installing the app for the first time after such changes

My iOS app is getting repeatedly rejected under Guideline 4.3(b) Spam. Apple says the app is astrology / horoscope category, but the app is actually a B2B partner dashboard for verified consultants and contains no horoscope content. We already: Removed astrology keywords Renamed the app Changed metadata Restricted login Removed China region Explained multiple times to App Review Still getting same rejection again and again. Has anyone successfully resolved 4.3(b) spam rejection for astrology / consultation / marketplace apps? What exact change finally worked? Should we appeal? Request call? Change bundle? New app? Different category? Need expert advice urgently.

I've been waiting for 1 month, and my family keeps telling me, "oh you lost your money" and i am starting to trust then, i quit my job just to work in apps and apple does not take it seriously, that was my last money, and i invested in my app, so i just wanted it to be reviewed. Please lets help yours community

We have returned your In-App Purchase products to you as the required binary was not submitted. When you are ready to submit the binary, please resubmit the In-App Purchase products with the binary. we have tried everything; there is no button to add for review.

When ever i accect Transfer the app it's said i need to sign the Alternative Terms Addendum for Apps in the EU even though i already sign it. Please help

I’m trying to submit my app for review, but I’m currently blocked due to a recurring issue with in-app subscriptions. Both of my auto-renewable subscriptions (premium_monthly and premium_yearly) are marked as “Waiting for Review”. However, I am still seeing the blue box stating that “your first subscription must be submitted with a new app version.” Despite creating a new version (1.0.1) and uploading/selecting a new build , I am not seeing the “In-App Purchases and Subscriptions” section on the version page, and I therefore cannot link the subscriptions before submitting. This issue is blocking my ability to submit the app for review. Any help to resolve this would be greatly appreciated.

Hi all, Looking for some clarity.. I have an app (Pocket Love: AI Roleplay Chat, Apple ID: 6745031268) that went through a long review process with many resubmissions. The feedback I received across those reviews was often generic “overtly sexual”) message, but without any detail on exactly what needed to change. Because of that, I approached it iteratively making adjustments each time based on what I thought the issue might be. Over time I made quite significant changes across the app (imagery, unlockable content, voice-overs, menus, copy, etc.), and increased the age rating to 18+. I also had a call with a policy eexpert & App Review. In the final interaction, I was asked to ensure all unlockable content was visible, so I re-uploaded a build and provided screenshots with everything pre-unlocked for transparency. Despite this, my account has now been flagged under 3.2(f) for “dishonest or fraudulent activity,” and is pending termination. What I’m struggling to understand is: Can repeated resubmissions / iterative changes alone be interpreted as “evasion” under 3.2(f)? Or does this typically mean App Review believes there was something intentionally misleading? From my perspective, I was trying to respond to feedback and get the app into a compliant state, not bypass review or hide anything. The game does have "sexy" imagery lingerie etc..and adult themes but 0 nudity and is tamer than similar games live on the app store. Would really appreciate any insight from others who’ve experienced similar, or from anyone familiar with how this is interpreted internally. I can't believe my account is pending termination without any intentional wrongdoing, I currently have 3 other live games one with strong revenue, that will be removed too due to this. My initial appeal was rejected today. Thanks!

Hello everyone, My app has been in "Waiting for Review" status since February 20, and it still hasn’t moved to the review stage yet. On March 9, I submitted a support ticket asking whether there might be any issue with my submission or if additional information is required from my side. However, I have not received any response from Apple so far. At this point, I’m not sure if I should continue waiting or if there is anything else I should do to resolve the situation. App ID: 6759365919 Ticket ID: 102839874589 If anyone has experienced a similar situation or if an Apple staff member could help check the status, I would really appreciate it. Thank you very much.

Hi, I’m running into a persistent issue in App Store Connect related to TestFlight and app reviews, and I’m hoping someone has seen this before. Around two weeks ago, I started getting the following error when trying to create external TestFlight builds: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Since then: I cannot create any external TestFlight tests Internal TestFlight builds appear, but cannot be downloaded (“The requested app is not available or doesn’t exist”) My apps do not progress properly through review One app got stuck in “In Review” for ~10 days; I eventually withdrew it and resubmitted it At this point, I cannot update two existing apps, and I can’t start testing a new app at all Important details: This is an individual developer account I am the Account Holder All contracts appear active and valid The issue affects multiple apps, not just one Nothing changed on my side (no contract updates, no account changes) before this started happening. I’ve already reached out to Apple Developer Support multiple times, but unfortunately haven’t received any response so far, which makes it unclear how to proceed. Has anyone experienced this issue or found a resolution? Any insight would be greatly appreciated. Thanks!

Hi all, Submitted first ever app for review to app store and got rejected. My app isn't live and I have demo accounts too which they seemed to use. For context my app is free on launch, no in app transactions, and it is a marriage app. What I did not account for is them going through apple sign in and right now I have no way to catch that so that account doesn't mix with real users. I've thought about adding a tap feature and disclosing it, so they tap something x times and it is marked as reviewer account, but that violates guideline 2.3.1. Also thought about adding just visible text for reviewers, but then real users would see that too so its a no go. Asked Claude and it says to try Sandbox Receipt Detection, which should work for a free app, but I'm not sure and would rather ask then implement, submit and find out it doesn't work. Appreciate any help y'all can give me! Thanks!